Patrick Elliott <sha### [at] hotmailcom> wrote:
> Just my own 2 cents, but A) if you can't get it to do what you want, how 
> is that versatile?

  I can't get POV-Ray to play me "happy birthday" from my soundcard, but
that doesn't mean POV-Ray's scripting language is not versatile.

  The "PCM4" format is an example of this versatility: I can very
easily include textures in the pcm file thanks to it.

> and B) last I checked #read is used for pulling in 
> data from a file, not SDL, which is more normally included with and 
> 'include' directive.

  Then check again. You can for example put a #declare in the input
file and POV-Ray will interpret it correctly.

> What you seem to be implying is that both the SDL parser and the #read 
> command use the same system to retrieve data and that because of this it 
> ignores the rules used by probably 90% of all programs, which nearly 
> universally consider newlines as a break in the data.

  How many programming languages can you mention which consider newline
as some kind of separator which is different from a space in their input
language?
  Does a HTML browser consider a newline in a HTML file as some kind of
separator different from a space?

  I wouldn't call it a "universal" fact that a newline character is a
separator in a data file.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message